home *** CD-ROM | disk | FTP | other *** search
XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) NNNNAAAAMMMMEEEE XXXXmmmmDDDDiiiissssppppllllaaaayyyy - The Display widget class SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS #include <Xm/Display.h> VVVVEEEERRRRSSSSIIIIOOOONNNN This page documents Motif 2.1. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN The XmDisplay object is used by the Motif widgets to store information that is specific to a display. It also allows the toolkit to access certain information on widget hierarchies that would otherwise be unavailable. Each client has one XmDisplay object for each display it accesses. An XmDisplay object is automatically created when the application creates the first shell on a display (usually accomplished by a call to XXXXttttAAAAppppppppIIIInnnniiiittttiiiiaaaalllliiiizzzzeeee or XXXXttttAAAAppppppppCCCCrrrreeeeaaaatttteeeeSSSShhhheeeellllllll). It is not necessary to create an XmDisplay object by any other means. An application can use the function XXXXmmmmGGGGeeeettttXXXXmmmmDDDDiiiissssppppllllaaaayyyy to obtain the widget ID of the XmDisplay object for a given display. An application cannot supply initial values for XmDisplay resources as arguments to a call to any function that creates widgets. The application or user can supply initial values in a resource file. After creating the first shell on the display, the application can use XXXXmmmmGGGGeeeettttXXXXmmmmDDDDiiiissssppppllllaaaayyyy to obtain the widget ID of the XmDisplay object and then call XXXXttttSSSSeeeettttVVVVaaaalllluuuueeeessss to set the XmDisplay resources. XmDisplay resources specify the drag protocol style for a client participating in drag and drop transactions. The two basic protocol types are preregister and dynamic. When a preregister protocol is used, the toolkit handles any communication between the initiator and receiver clients and displays the appropriate drag-over and drag-under visual effects. A client registers its drop sites in advance and this information is stored in a property for each top-level window. When the drag pointer enters a top-level window, the drop site information is read by the initiator. A dynamic protocol allows the source and destination clients to dynamically communicate drag and drop state information between each other, and to update their respective visuals accordingly. The toolkit provides drop site information as the pointer passes over any given drop site. In this mode, a receiver can supply a procedure to generate its own drag- under effects. CCCCllllaaaasssssssseeeessss Display inherits behavior and resources from CCCCoooorrrreeee, Page 1 (printed 10/3/02) XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) CCCCoooommmmppppoooossssiiiitttteeee, SSSShhhheeeellllllll, WWWWMMMMSSSShhhheeeellllllll, VVVVeeeennnnddddoooorrrrSSSShhhheeeellllllll, TTTTooooppppLLLLeeeevvvveeeellllSSSShhhheeeellllllll, and AAAApppppppplllliiiiccccaaaattttiiiioooonnnnSSSShhhheeeellllllll classes. The class pointer is _x_m_D_i_s_p_l_a_y_C_l_a_s_s. The class name is XXXXmmmmDDDDiiiissssppppllllaaaayyyy. NNNNeeeewwww RRRReeeessssoooouuuurrrrcccceeeessss The following table defines a set of widget resources used by the programmer to specify data. The programmer can also set the resource values for the inherited classes to set attributes for this widget. To reference a resource by name or by class in a ....XXXXddddeeeeffffaaaauuuullllttttssss file, remove the XXXXmmmmNNNN or XXXXmmmmCCCC prefix and use the remaining letters. To specify one of the defined values for a resource in a ....XXXXddddeeeeffffaaaauuuullllttttssssfile, remove the XXXXmmmm prefix and use the remaining letters (in either lowercase or uppercase, but include any underscores between words). The codes in the access column indicate if the given resource can be set at creation time (C), set by using XtSetValues (S), retrieved by using XtGetValues (G), or is not applicable (N/A). XXXXmmmmDDDDiiiissssppppllllaaaayyyy RRRReeeessssoooouuuurrrrcccceeee SSSSeeeetttt NNNNaaaammmmeeee CCCCllllaaaassssssss TTTTyyyyppppeeee DDDDeeeeffffaaaauuuulllltttt AAAAcccccccceeeessssssss XmNdefaultButtonEmphasis XmCDefaultButtonEmphasis XtEnum XmEXTERNAL_HIGHLIGHT C XmNdefaultVirtualBindings XmCDefaultVirtualBindings String dynamic C XmNdragInitiatorProtocolStyle XmCDragInitiatorProtocolStyle unsigned char XmDRAG_PREFER_RECEIVER CG XmNdragReceiverProtocolStyle XmCDragReceiverProtocolStyle unsigned char XmDRAG_PREFER_DYNAMIC CG XmNdragStartCallback XmCCallback XtCallbackList NULL C XmNenableBtn1Transfer XmCEnableBtn1Transfer XtEnum XmOFF C XmNenableButtonTab XmCEnableButtonTab Boolean False C XmNenableDragIcon XmCEnableDragIcon Boolean False C XmNenableEtchedInMenu XmCEnableEtchedInMenu Boolean False C XmNenableToggleColor XmCEnableToggleColor Boolean False C XmNenableToggleVisual XmCEnableToggleVisual Boolean False C XmNenableUnselectableDrag XmCEnableUnselectableDrag Boolean True C XmNenableWarp XmCEnableWarp XtEnum True CSG XmNmotifVersion XmCMotifVersion int XmVERSION CSG XmNnoFontCallback XmCCallback XtCallbackList NULL C XmNnoRenditionCallback XmCCallback XtCallbackList NULL C XmNuserData XmCUserData XtPointer NULL CSG XXXXmmmmNNNNddddeeeeffffaaaauuuullllttttBBBBuuuuttttttttoooonnnnEEEEmmmmpppphhhhaaaassssiiiissss Specifies whether to change the look of the PushButton widget and gadget that have the XXXXmmmmNNNNsssshhhhoooowwwwAAAAssssDDDDeeeeffffaaaauuuulllltttt resource set. When the PushButton is the default, it has an etched out button which is enclosed with another etched in border. The XXXXmmmmNNNNddddeeeeffffaaaauuuullllttttBBBBuuuuttttttttoooonnnnEEEEmmmmpppphhhhaaaassssiiiissss has the follow possible values, which affect the location cursor: XXXXmmmmIIIINNNNTTTTEEEERRRRNNNNAAAALLLL____HHHHIIIIGGGGHHHHLLLLIIIIGGGGHHHHTTTT Page 2 (printed 10/3/02) XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) Causes the location cursor to appear in between the two etched borders to minimize the space required. XXXXmmmmEEEEXXXXTTTTEEEERRRRNNNNAAAALLLL____HHHHIIIIGGGGHHHHLLLLIIIIGGGGHHHHTTTT Causes the PushButton to draw the location cursor outside the second border. XXXXmmmmNNNNddddeeeeffffaaaauuuullllttttVVVViiiirrrrttttuuuuaaaallllBBBBiiiinnnnddddiiiinnnnggggssss Specifies the default virtual bindings for the display. Following is an example of a specification for the ddddeeeeffffaaaauuuullllttttVVVViiiirrrrttttuuuuaaaallllBBBBiiiinnnnddddiiiinnnnggggssss resource in a resource file: *defaultVirtualBindings: \ osfBackSpace: <Key>BackSpace \n\ osfInsert: <Key>InsertChar \n\ osfDelete: <Key>DeleteChar \n\ ... osfLeft: <Key>left, Ctrl<Key>H XXXXmmmmNNNNddddrrrraaaaggggIIIInnnniiiittttiiiiaaaattttoooorrrrPPPPrrrroooottttooooccccoooollllSSSSttttyyyylllleeee Specifies the drag and drop protocol requirements or preference when the client is an initiator. The possible values are XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR As an initiator, this client does not use the dynamic protocol and can only arrange visual effects with receivers who provide preregistered information. XXXXmmmmDDDDRRRRAAAAGGGG____DDDDYYYYNNNNAAAAMMMMIIIICCCC As an initiator, this client does not make use of any preregistered drop site information made available by other clients, and can only arrange visual effects with receivers who use the dynamic protocol. XXXXmmmmDDDDRRRRAAAAGGGG____NNNNOOOONNNNEEEE Specifies that drag and drop is disabled for this client. XXXXmmmmDDDDRRRRAAAAGGGG____DDDDRRRROOOOPPPP____OOOONNNNLLLLYYYY As an initiator, this client does not use either the preregistered drop site information or the dynamic protocol. It supports dragging, and any time the cursor is over a client that supports drag and drop, valid feedback is Page 3 (printed 10/3/02) XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) provided. There are no other visual effects. XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____DDDDYYYYNNNNAAAAMMMMIIIICCCC As an initiator, this client can support both the preregister and dynamic protocols, but prefers to use dynamic protocols whenever possible in order to provide high-quality drag-under feedback. XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR As an initiator, this client can support both the preregister and dynamic protocols, but prefers to use the preregister protocol whenever possible in order to accommodate performance needs or to provide consistent drag-over feedback. XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____RRRREEEECCCCEEEEIIIIVVVVEEEERRRR Indicates that this client can support both preregister and dynamic protocols, but will defer to the preference of the receiver client. This value is valid only for the XXXXmmmmNNNNddddrrrraaaaggggIIIInnnniiiittttiiiiaaaattttoooorrrrPPPPrrrroooottttooooccccoooollllSSSSttttyyyylllleeeeresource, and is its default value. XXXXmmmmNNNNddddrrrraaaaggggRRRReeeecccceeeeiiiivvvveeeerrrrPPPPrrrroooottttooooccccoooollllSSSSttttyyyylllleeee Specifies the drag and drop protocol requirements or preference when this client is a receiver. The values are XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR As a receiver, this client preregisters drop site information and does not use the dynamic protocol. It can only arrange visual effects with initiators who make use of the preregistered information. XXXXmmmmDDDDRRRRAAAAGGGG____DDDDYYYYNNNNAAAAMMMMIIIICCCC As a receiver, this client uses the dynamic protocol and does not preregister drop site information. It can only arrange visual effects with initiators who use the dynamic protocol. XXXXmmmmDDDDRRRRAAAAGGGG____NNNNOOOONNNNEEEE Specifies that drag and drop is disabled for this client. Page 4 (printed 10/3/02) XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) XXXXmmmmDDDDRRRRAAAAGGGG____DDDDRRRROOOOPPPP____OOOONNNNLLLLYYYY As a receiver, this client neither uses the dynamic protocol nor preregisters drop site information. It supports dropping, and when dragging over this client, valid feedback is always provided, but there are no other visual effects. XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____DDDDYYYYNNNNAAAAMMMMIIIICCCC As a receiver, this client can support both the preregister and dynamic protocols, but prefers to use the dynamic protocol whenever possible in order to provide high-quality drag-under feedback. XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR As a receiver, this client can support both the preregister and dynamic protocols, but prefers to use the preregister protocol whenever possible in order to accommodate performance needs. The default value of this resource is dependent on the capabilities of the display. If the display supports the shape extension, allowing the dynamic protocol to use arbitrarily sized drag cursors, the default of this resource is XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____DDDDYYYYNNNNAAAAMMMMIIIICCCC, otherwise the default is XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR. The actual protocol used between an initiator and a receiver is based on the protocol style of the receiver and initiator. The decision matrix is described in the following table. DDDDrrrraaaagggg RRRReeeecccceeeeiiiivvvveeeerrrr PPPPrrrroooottttooooccccoooollll SSSSttttyyyylllleeee PPPPrrrreeeerrrreeeeggggiiiisssstttteeeerrrr PPPPrrrreeeeffffeeeerrrr PPPPrrrreeeerrrreeeeggggiiiisssstttteeeerrrr PPPPrrrreeeeffffeeeerrrr DDDDyyyynnnnaaaammmmiiiicccc DDDDyyyynnnnaaaammmmiiiicccc Preregister Preregister Preregister Drop Only DDDDrrrraaaagggg IIIInnnniiiittttiiiiaaaattttoooorrrr Preregister Preregister Preregister Dynamic Preregister Preregister Dynamic Dynamic Preregister Dynamic Dynamic Dynamic DDDDrrrroooopppp OOOOnnnnllllyyyy DDDDyyyynnnnaaaammmmiiiicccc DDDDyyyynnnnaaaammmmiiiicccc DDDDyyyynnnnaaaammmmiiiicccc The value XXXXmmmmDDDDRRRRAAAAGGGG____NNNNOOOONNNNEEEE does not appear in the matrix. When specified for either the initiator or receiver side, XXXXmmmmDDDDRRRRAAAAGGGG____NNNNOOOONNNNEEEE implies that drag and drop transactions are not supported. A value of XXXXmmmmDDDDRRRRAAAAGGGG____DDDDRRRROOOOPPPP____OOOONNNNLLLLYYYY (Drop Only) results when an initiator and receiver cannot compromise protocol Page 5 (printed 10/3/02) XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) styles, that is, one client requires dynamic mode while the other can only support preregister mode, or if either explicitly has specified XXXXmmmmDDDDRRRRAAAAGGGG____DDDDRRRROOOOPPPP____OOOONNNNLLLLYYYY. XXXXmmmmNNNNddddrrrraaaaggggSSSSttttaaaarrrrttttCCCCaaaallllllllbbbbaaaacccckkkk Specifies the list of callbacks that are invoked when the XXXXmmmmDDDDrrrraaaaggggSSSSttttaaaarrrrtttt function is called. The type of structure whose address is passed to this callback is XXXXmmmmDDDDrrrraaaaggggSSSSttttaaaarrrrttttCCCCaaaallllllllbbbbaaaacccckkkkSSSSttttrrrruuuucccctttt. The callback reason is XXXXmmmmCCCCRRRR____DDDDRRRRAAAAGGGG____SSSSTTTTAAAARRRRTTTT. XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeBBBBttttnnnn1111TTTTrrrraaaannnnssssffffeeeerrrr Specifies if selection and transfer actions are integrated on Btn1 and extend actions are activated on Btn2. This resource can take the following values: XXXXmmmmOOOOFFFFFFFF Disables integration and selection activation on Btn1. _X_m_B_U_T_T_O_N_2__T_R_A_N_S_F_E_R Enables integration and selection activation on Btn1 and transfer on Btn2. _X_m_B_U_T_T_O_N_2__A_D_J_U_S_T Enables integration and selection activation on Btn1 and adjust on Btn2. This resource affects the actions of Text, TextField, List, and Container. XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeBBBBuuuuttttttttoooonnnnTTTTaaaabbbb Specifies if the action for the <<<<TTTTaaaabbbb>>>> key (KKKKNNNNeeeexxxxttttFFFFiiiieeeelllldddd and KKKKPPPPrrrreeeevvvvFFFFiiiieeeelllldddd actions) is to be modified. A value of True modifies the key to move as an arrow key until the boundary of a tab group is reached. Then, at the boundary of the tab group, KKKKNNNNeeeexxxxttttFFFFiiiieeeelllldddd and KKKKPPPPrrrreeeevvvvFFFFiiiieeeelllldddd will move to the next or previous tab group, respectively. A value of False does not cause modification. XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeDDDDrrrraaaaggggIIIIccccoooonnnn Specifies which set of icons are to be used for system default cursors during drag and drop operations. A value of False specifies that earlier versions of Motif release icons are used, a value of True specifies that alternate icons are used. This resource affects both the 16x16 and the 32x32 icons that the system defaults for each of the Screen objects associated with this display. Page 6 (printed 10/3/02) XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeEEEEttttcccchhhheeeeddddIIIInnnnMMMMeeeennnnuuuu Specifies the shadowing of the button widgets and gadgets in menus when the control is activated. A value of True causes the selected menu to be drawn with the shadow etched in; this shadow style is consistent with the selected appearance of other button widgets outside of menus. A value of False causes the selected menu to be draw with the shadow etched out. This resource affects the actions of PushButton, ToggleButton, and CascadeButton widgets and gadgets when they are children of Menu. When this resource is set, the background of a button in a menu uses the XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrr(derived from the XXXXmmmmNNNNsssseeeelllleeeeccccttttPPPPiiiixxxxeeeellll) when armed as a default. A PPPPuuuusssshhhhBBBBuuuuttttttttoooonnnnuses the XXXXmmmmNNNNaaaarrrrmmmmCCCCoooolllloooorrrrif it is defined. A TTTToooogggggggglllleeeeBBBBuuuuttttttttoooonnnnuses the XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrrif XXXXmmmmNNNNiiiinnnnddddiiiiccccaaaattttoooorrrrOOOOnnnnis FFFFaaaallllsssseeee and XXXXmmmmNNNNffffiiiillllllllOOOOnnnnSSSSeeeelllleeeeccccttttis TTTTrrrruuuueeee. XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeTTTToooogggggggglllleeeeCCCCoooolllloooorrrr Specifies how to determine the default value of the XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrr resource of ToggleButton and ToggleButtonGadget. A value of True causes the default value of XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrrto be set to the value of XXXXmmmmNNNNhhhhiiiigggghhhhlllliiiigggghhhhttttCCCCoooolllloooorrrr. A value of False causes the default value of XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrrto be set to the value of XXXXmmmmNNNNbbbbaaaacccckkkkggggrrrroooouuuunnnndddd. This resource only affects the appearance of ToggleButton widgets and gadgets that are in XXXXmmmmOOOONNNNEEEE____OOOOFFFF____MMMMAAAANNNNYYYY or XXXXmmmmOOOONNNNEEEE____OOOOFFFF____MMMMAAAANNNNYYYY____RRRROOOOUUUUNNNNDDDD mode. In addition, XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeTTTToooogggggggglllleeeeCCCCoooolllloooorrrronly influences the default value of XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrr. That is, if the user or application sets a value for XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrr, then XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeTTTToooogggggggglllleeeeCCCCoooolllloooorrrr is ignored. XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeTTTToooogggggggglllleeeeVVVViiiissssuuuuaaaallll Specifies the visual appearance of the ToggleButton widget and/or gadget. This resource affects the default value of the ToggleButton[Gadget] XXXXmmmmNNNNiiiinnnnddddiiiiccccaaaattttoooorrrrTTTTyyyyppppeeee and XXXXmmmmNNNNiiiinnnnddddiiiiccccaaaattttoooorrrrOOOOnnnn resources. When the ToggleButton is in a RadioBox, a value of True causes the XXXXmmmmOOOONNNNEEEE____OOOOFFFF____MMMMAAAANNNNYYYY____RRRROOOOUUUUNNNNDDDD (a shadowed circle) to be the default. Otherwise, when this resource is True, the ToggleButton XXXXmmmmNNNNiiiinnnnddddiiiiccccaaaattttoooorrrrOOOOnnnn resource causes a default of XXXXmmmmNNNN____OOOOFFFF____MMMMAAAANNNNYYYY, which will be a shadowed square with a check mark (check box). A value of False causes the following: XXXXmmmmOOOONNNNEEEE____OOOOFFFF____MMMMAAAANNNNYYYY Page 7 (printed 10/3/02) XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) Is a shadowed diamond. XXXXmmmmNNNN____OOOOFFFF____MMMMAAAANNNNYYYY Is a shadowed square. XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeUUUUnnnnsssseeeelllleeeeccccttttaaaabbbblllleeeeDDDDrrrraaaagggg Specifies whether or not it is possible to drag from Label and Scale. A value of True enables the drag; a value of False disables it. XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeWWWWaaaarrrrpppp Specifies if an application is allowed to warp the pointer from the user. A value of True enables warping, a value of False does not. XXXXmmmmNNNNmmmmoooottttiiiiffffVVVVeeeerrrrssssiiiioooonnnn Specifies the current version of Motif that the current implementation is supposed to behave like. By default, this resource gets its value from release values in XXXXmmmm....hhhh. XXXXmmmmNNNNnnnnooooFFFFoooonnnnttttCCCCaaaallllllllbbbbaaaacccckkkk This callback is called whenever a rendition attempts to load a font or fontset and fails. This can happen on creation if the font is specified as XXXXmmmmLLLLOOOOAAAADDDD____IIIIMMMMMMMMEEEEDDDDIIIIAAAATTTTEEEE or when an attempt is made to render an XXXXmmmmSSSSttttrrrriiiinnnngggg using a font specified as XXXXmmmmLLLLOOOOAAAADDDD____DDDDEEEEFFFFEEEERRRRRRRREEEEDDDD. An application can have this callback attempt to remedy this problem by calling XXXXmmmmRRRReeeennnnddddiiiittttiiiioooonnnnUUUUppppddddaaaatttteeee on the input rendition to provide a font for the widget to use. This may be done by either providing an an alternative font name to be loaded using the XXXXmmmmNNNNffffoooonnnnttttNNNNaaaammmmeeee and XXXXmmmmNNNNffffoooonnnnttttTTTTyyyyppppeeee resources or with an already loaded font using the XXXXmmmmNNNNffffoooonnnntttt resource. The callback reason is XXXXmmmmCCCCRRRR____NNNNOOOO____FFFFOOOONNNNTTTT. This callback uses the XXXXmmmmDDDDiiiissssppppllllaaaayyyyCCCCaaaallllllllbbbbaaaacccckkkkSSSSttttrrrruuuucccctttt structure. XXXXmmmmNNNNnnnnooooRRRReeeennnnddddiiiittttiiiioooonnnnCCCCaaaallllllllbbbbaaaacccckkkk This callback is called whenever an attempt is made to render a segment with a _R_E_N_D_I_T_I_O_N tag which does not match any renditions in a given render table. The callback reason is XXXXmmmmCCCCRRRR____NNNNOOOO____RRRREEEENNNNDDDDIIIITTTTIIIIOOOONNNN. This callback uses the XXXXmmmmDDDDiiiissssppppllllaaaayyyyCCCCaaaallllllllbbbbaaaacccckkkkSSSSttttrrrruuuucccctttt structure. An application can have this callback attempt to remedy this problem by creating a new rendition with the given tag and adding it to rrrreeeennnnddddeeeerrrr____ttttaaaabbbblllleeee. The XXXXmmmmNNNNnnnnooooRRRReeeennnnddddiiiittttiiiioooonnnnCCCCaaaallllllllbbbbaaaacccckkkk should deallocate the render table passed in in the rrrreeeennnnddddeeeerrrr____ttttaaaabbbblllleeee field Page 8 (printed 10/3/02) XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) of the callback structure. Note that the table will automatically be deallocated if the XXXXmmmmRRRReeeennnnddddeeeerrrrTTTTaaaabbbblllleeeeAAAAddddddddRRRReeeennnnddddiiiittttiiiioooonnnnssss function is called on it. The callback should NOT deallocate the modified render table that is passed back to Motif in the rrrreeeennnnddddeeeerrrr____ttttaaaabbbblllleeeefield. If the application wishes to manipulate this render table further, it should make a copy with the XXXXmmmmRRRReeeennnnddddeeeerrrrTTTTaaaabbbblllleeeeCCCCooooppppyyyy function before returning from the callback. XXXXmmmmNNNNuuuusssseeeerrrrDDDDaaaattttaaaa Specifies a client data pointer for applications. An internally unused resource. IIIInnnnhhhheeeerrrriiiitttteeeedddd RRRReeeessssoooouuuurrrrcccceeeessss All of the superclass resources inherited by XmDisplay are designated N/A (not applicable). CCCCaaaallllllllbbbbaaaacccckkkk IIIInnnnffffoooorrrrmmmmaaaattttiiiioooonnnn A pointer to the following structure is passed to the XXXXmmmmNNNNddddrrrraaaaggggSSSSttttaaaarrrrttttCCCCaaaallllllllbbbbaaaacccckkkk callback: typedef struct { int _r_e_a_s_o_n; XEvent *_e_v_e_n_t; Widget _t_i_m_e_S_t_a_m_p; Boolean _d_o_i_t; }XmDragStartCallbackStruct; _r_e_a_s_o_n Indicates why the callback was invoked _e_v_e_n_t Points to the _X_E_v_e_n_t that triggered the callback _w_i_d_g_e_t Indicates the ID of the widget from which the drag was initiated. _d_o_i_t Is an IN/OUT member that allows the callback to determine whether to continue with the drag or cancel. Setting _d_o_i_t to False will cancel the drag. The default value is NULL. A pointer to the following structure is passed to the XXXXmmmmNNNNnnnnooooFFFFoooonnnnttttCCCCaaaallllllllbbbbaaaacccckkkk and XXXXmmmmNNNNnnnnooooRRRReeeennnnddddiiiittttiiiioooonnnnCCCCaaaallllllllbbbbaaaacccckkkk callbacks: typedef struct { int _r_e_a_s_o_n; XEvent *_e_v_e_n_t; XmRendition _r_e_n_d_i_t_i_o_n; char *_f_o_n_t__n_a_m_e; XmRenderTable _r_e_n_d_e_r__t_a_b_l_e; Page 9 (printed 10/3/02) XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX)))) XmStringTag _t_a_g; }XmDisplayCallbackStruct; _r_e_a_s_o_n Indicates why the callback was invoked. _e_v_e_n_t Points to the _X_E_v_e_n_t that triggered the callback. It can be NULL. _r_e_n_d_i_t_i_o_n Specifies the rendition with the missing font. _f_o_n_t__n_a_m_e Specifies the name of the font or font set which could not be loaded. rrrreeeennnnddddeeeerrrr____ttttaaaabbbblllleeee Specifies the render table with the missing rendition. _t_a_g Specifies the tag of the missing rendition. The following table describes the reasons for which the individual callback structure fields are valid. RRRReeeeaaaassssoooonnnn VVVVaaaalllliiiidddd FFFFiiiieeeellllddddssss XmCR_NO_FONT _r_e_n_d_i_t_i_o_n, _f_o_n_t__n_a_m_e XmCR_NO_RENDITION _r_e_n_d_e_r__t_a_b_l_e, _t_a_g RRRREEEELLLLAAAATTTTEEEEDDDD AAAApppppppplllliiiiccccaaaattttiiiioooonnnnSSSShhhheeeellllllll(3), CCCCoooommmmppppoooossssiiiitttteeee(3), CCCCoooorrrreeee(3), TTTTooooppppLLLLeeeevvvveeeellllSSSShhhheeeellllllll(3), VVVVeeeennnnddddoooorrrrSSSShhhheeeellllllll(3), WWWWMMMMSSSShhhheeeellllllll(3), XXXXmmmmGGGGeeeettttXXXXmmmmDDDDiiiissssppppllllaaaayyyy(3), and XXXXmmmmSSSSccccrrrreeeeeeeennnn(3). Page 10 (printed 10/3/02) 
